Skip to content

vschema: allow pins in vschema#4134

Merged
sougou merged 1 commit intovitessio:masterfrom
sougou:pin
Aug 16, 2018
Merged

vschema: allow pins in vschema#4134
sougou merged 1 commit intovitessio:masterfrom
sougou:pin

Conversation

@sougou
Copy link
Copy Markdown
Contributor

@sougou sougou commented Aug 14, 2018

Pinning was an internal feature used for pinning the
dual table to shard 0. Exposing this ability in vschema
allows someone to pin an unsharded table to a specific
shard.

This is still not a full feature because we ned to
think about the various use cases like resharding etc.
But it can be used for testing purposes.

Signed-off-by: Sugu Sougoumarane ssougou@gmail.com

Pinning was an internal feature used for pinning the
dual table to shard 0. Exposing this ability in vschema
allows someone to pin an unsharded table to a specific
shard.

This is still not a full feature because we ned to
think about the various use cases like resharding etc.
But it can be used for testing purposes.

Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
@sougou sougou requested review from demmer and rafael August 14, 2018 23:56
@demmer
Copy link
Copy Markdown
Member

demmer commented Aug 15, 2018

I see nothing wrong with the code but I'm unconvinced by the motivations for why someone would want to do this? Wouldn't it be better to put all unsharded tables into a separate unsharded keyspace?

@sougou
Copy link
Copy Markdown
Contributor Author

sougou commented Aug 15, 2018

This is for those who are transitioning from bare-metal single mysql per machine type of setup. A separate keyspace becomes very expensive because they don't have the process in place to spin up multiple mysql instances per box.

There is also the argument that you don't want to create a keyspace just to store a single-row sequence table.

Copy link
Copy Markdown
Member

@demmer demmer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. That all makes sense. Lgtm

@sougou sougou merged commit c3159d9 into vitessio:master Aug 16, 2018
@sougou sougou deleted the pin branch August 16, 2018 01:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants